Branch Transformation API

/kiosk/account-inquiry.get

An acquirer will have one AcquirerInstitutionIdCode _but may be provided multiple _PseudoTerm for different devices, or consumers of the service.

The combination of the AcquirerInstitutionIdCode and the PseudoTerm are used to identify the routing, product identification, and CO-OP billing configuration.

/kiosk/deposit

Requests deposit funds to a member’s account. The deposit can be cash, checks (drafts), or a combination of both. The issuer receives the member number and account id. In addition, the issuer receives information about the deposit hold categories. The issuer can approve or deny the deposit. The issuer returns the balance information in addition to the response code.

An acquirer will have one AcquirerInstitutionIdCode but may be provided multiple PseudoTerm for different devices, or consumers of the service.

MICR Information is not required for deposits, however if the acquirer chooses to provide MICR information, each check object must contain all data elements.

Sender data is rarely included in Shared Branching Messages, however, the specification requires that these data elements be available.

Receiver data is rarely included in Shared Branching Messages, however, the specification requires that these data elements be available.

/kiosk/member-verify

Retrieves member information. The issuer receives the member number and locates the member’s account information and returns the data in the response. Account information returned can vary based upon the network the Issuer is within. The network of an Issuer can be determined by the network ID associated with their PAN that is returned in the Service List Institutions call.

/kiosk/service-list.get

Requests the BIN file. This is a list of all financial institutions that participate in a particular channel service. The list can be used to display to the member prior to requesting the Auth Process to authorize a member of a particular financial institution.

/kiosk/transfer.get

Call will transfer funds from either a deposit or a loan account to another deposit or loan account. The issuer receives the member number, the “from account id” and the “to account id”. The issuer system validates that there are enough funds available in the “from account” and moves the money to the “to account”. The issuer returns the balance information in addition to the response code.

/kiosk/payments.get

Requests to make a payment to member’s account. The payment can be cash, checks (drafts), or a combination of both. The issuer receives the member number and account id. In addition, the issuer receives information about the deposit hold categories. The issuer can approve or deny the payment. The issuer returns the balance information in addition to the response code.

/kiosk/withdrawal

Requests a withdrawal of funds from an account. The withdrawal can be for either cash or for goods such as a check. The issuer receives the member number and the account id. The issuer validates that there are enough funds in the member’s account and approves or denies the transaction accordingly. The issuer returns the balance information in addition to the response code.

/kiosk/reversal

A transaction that is successful -- with a response of "00" from the Issuer -- may still fail for any other reason. When a transaction fails, the transaction must trigger a reversal. For instance, a deposit that fails requires a withdrawal be booked, to be settled correctly.